-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Byte-shave and deduplicate infinite query implementation #4804
Merged
markerikson
merged 19 commits into
feature/infinite-query-integration
from
feature/infinite-query-bundle-size
Jan 5, 2025
Merged
Byte-shave and deduplicate infinite query implementation #4804
markerikson
merged 19 commits into
feature/infinite-query-integration
from
feature/infinite-query-bundle-size
Jan 5, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
markerikson
force-pushed
the
feature/infinite-query-bundle-size
branch
from
January 3, 2025 23:08
337e06f
to
f7754b2
Compare
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit f93bec9:
|
markerikson
force-pushed
the
feature/infinite-query-bundle-size
branch
from
January 3, 2025 23:34
60668fb
to
eb56619
Compare
size-limit report 📦
|
markerikson
force-pushed
the
feature/infinite-query-bundle-size
branch
from
January 5, 2025 21:57
85d9820
to
249e0ec
Compare
markerikson
changed the title
[DRAFT] Byte-shave and deduplicate infinite query implementation
Byte-shave and deduplicate infinite query implementation
Jan 5, 2025
markerikson
merged commit Jan 5, 2025
968db05
into
feature/infinite-query-integration
84 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
Note that some of the byte-shaving is not actually related to this PR, and could be applied to
master
.Progress thus far, checking sizes via a Vite React app based off our default template (which has a couple normal query endpoints, but no infinite query endpoints. Note that the size increase is still expected because none of this can tree-shake, so you pay the cost regardless of whether or not you have any infinite queries.
Overall, we started with +7K min on the integration branch, and I've shaved off 1.27K min of that. I think I can knock off a few hundred bytes more working on the query hooks.
Sonda visualizations
2.5.0:
Integration:
Through initiate deduplication:
With hooks deduplicated: